Apparatus and Method for Diagnostic use of BIOS Attributes to Remediate Configuration Issues

ABSTRACT

An information handling system includes a storage device and a processor. The storage device stores Power-On Self Test (POST) code, diagnostic code, and remediation code. The POST code determines whether an error occurred while booting the information handling system. If an error occurred, the diagnostic code determines whether the error is associated with a configuration setting of the information handling system being in a first state. If the error is associated with the configuration setting being in the first state, the remediation code changes the first configuration setting from the first state to a second state, and reboots the information handling system.

FIELD OF THE DISCLOSURE

This disclosure generally relates to information handling systems, andmore particularly relates to the diagnostic use of BIOS attributes toremediate configuration issues.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, and/or communicatesinformation or data for business, personal, or other purposes. Becausetechnology and information handling needs and requirements may varybetween different applications, information handling systems may alsovary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information may be processed, stored, orcommunicated. The variations in information handling systems allow forinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing,reservations, enterprise data storage, or global communications. Inaddition, information handling systems may include a variety of hardwareand software resources that may be configured to process, store, andcommunicate information and may include one or more computer systems,data storage systems, and networking systems.

SUMMARY

A POST code may determine whether an error occurred while booting aninformation handling system. If an error occurred, diagnostic code maydetermine whether the error is associated with a configuration settingof the information handling system being in a first state. If the erroris associated with the configuration setting being in the first state,remediation code may change the first configuration setting from thefirst state to a second state, and reboot the information handlingsystem.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures have not necessarily been drawn toscale. For example, the dimensions of some of the elements areexaggerated relative to other elements. Embodiments incorporatingteachings of the present disclosure are shown and described with respectto the drawings presented herein, in which:

FIG. 1 is a block diagram of an information handling system according toan embodiment of the present disclosure;

FIG. 2 is a block diagram of BIOS/EFI code of the information handlingsystem of FIG. 1; and

FIGS. 3 and 4 are flowcharts of a method for the diagnostic use of BIOSattributes to remediate configuration issues according to an embodimentof the present disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF DRAWINGS

The following description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The followingdiscussion will focus on specific implementations and embodiments of theteachings. This focus is provided to assist in describing the teachings,and should not be interpreted as a limitation on the scope orapplicability of the teachings. However, other teachings can certainlybe used in this application. The teachings can also be used in otherapplications, and with several different types of architectures, such asdistributed computing architectures, client/server architectures, ormiddleware server architectures and associated resources.

FIG. 1 illustrates an embodiment of an information handling system 100including processors 102 and 104, a chipset 110, a memory 120, agraphics adapter 130 connected to a video display 134, a non-volatileRAM (NV-RAM) 140 that includes a basic input and outputsystem/extensible firmware interface (BIOS/EFI) module 142, a diskcontroller 150, a hard disk drive (HDD) 154, an optical disk drive 156,a disk emulator 160 connected to a solid state drive (SSD) 164, aninput/output (I/O) interface 170 connected to an add-on resource 174 anda trusted platform module (TPM 176, a network interface 180, and abaseboard management controller (BMC) 190. Processor 102 is connected tochipset 110 via processor interface 106, and processor 104 is connectedto the chipset via processor interface 108. In a particular embodiment,processors 102 and 104 are connected together via a high-capacitycoherent fabric, such as a HyperTransport link, a QuickPathInterconnect, or the like.

Chipset 110 represents an integrated circuit or group of integratedcircuits that manages the data flows between processors 102 and 104 andthe other elements of information handling system 100. In a particularembodiment, chipset 110 represents a pair of integrated circuits, suchas a northbridge component and a southbridge component. In anotherembodiment, some or all of the functions and features of chipset 110 areintegrated with one or more of processors 102 and 104. Memory 120 isconnected to chipset 110 via a memory interface 122. An example ofmemory interface 122 includes a Double Data Rate (DDR) memory channeland memory 120 represents one or more DDR Dual In-Line Memory Modules(DIMMs). In a particular embodiment, memory interface 122 represents twoor more DDR channels. In another embodiment, one or more of processors102 and 104 include a memory interface that provides a dedicated memoryfor the processors. A DDR channel and the connected DDR DIMMs can be inaccordance with a particular DDR standard, such as a DDR3 standard, aDDR4 standard, a DDR5 standard, or the like. Memory 120 may furtherrepresent various combinations of memory types, such as Dynamic RandomAccess Memory (DRAM) DIMMs, Static Random Access Memory (SRAM) DIMMs,non-volatile DIMMs (NV-DIMMs), storage class memory devices, Read-OnlyMemory (ROM) devices, or the like.

Graphics adapter 130 is connected to chipset 110 via a graphicsinterface 132, and provides a video display output 136 to a videodisplay 134. An example of a graphics interface 132 includes aPeripheral Component Interconnect-Express (PCIe) interface and graphicsadapter 130 can include a four lane (×4) PCIe adapter, an eight lane(×8) PCIe adapter, a 16-lane (×16) PCIe adapter, or anotherconfiguration, as needed or desired. In a particular embodiment,graphics adapter 130 is provided down on a system printed circuit board(PCB). Video display output 136 can include a Digital Video Interface(DVI), a High-Definition Multimedia Interface (HDMI), a DisplayPortinterface, or the like, and video display 134 can include a monitor, asmart television, an embedded display such as a laptop computer display,or the like.

NV-RAM 140, disk controller 150, and I/O interface 170 are connected tochipset 110 via an I/O channel 112. An example of I/O channel 112includes one or more point-to-point PCIe links between chipset 110 andeach of NVRAM 140, disk controller 150, and I/O interface 170. Chipset110 can also include one or more other I/O interfaces, including anIndustry Standard Architecture (ISA) interface, a Small Computer SerialInterface (SCSI) interface, an Inter-Integrated Circuit (I²C) interface,a System Packet Interface (SPI), a Universal Serial Bus (USB), anotherinterface, or a combination thereof. NV-RAM 140 includes BIOS/EFI module142 that stores machine-executable code (BIOS/EFI code) that operates todetect the resources of information handling system 100, to providedrivers for the resources, to initialize the resources, and to providecommon access mechanisms for the resources. The functions and featuresof BIOS/EFI module 142 will be further described below.

Disk controller 150 includes a disk interface 152 that connects the disccontroller to a hard disk drive (HDD) 154, to an optical disk drive(ODD) 156, and to disk emulator 160. An example of disk interface 152includes an Integrated Drive Electronics (IDE) interface, an AdvancedTechnology Attachment (ATA) such as a parallel ATA (PATA) interface or aserial ATA (SATA) interface, a SCSI interface, a USB interface, aproprietary interface, or a combination thereof. Disk emulator 160permits a solid-state drive (SSD) 164 to be connected to informationhandling system 100 via an external interface 162. An example ofexternal interface 162 includes a USB interface, an IEEE 1394 (Firewire)interface, a proprietary interface, or a combination thereof.Alternatively, solid-state drive 164 can be disposed within informationhandling system 100.

I/O interface 170 includes a peripheral interface 172 that connects theI/O interface to add-on resource 174, to TPM 176, and to networkinterface 180. Peripheral interface 172 can be the same type ofinterface as I/O channel 112, or can be a different type of interface.As such, I/O interface 170 extends the capacity of I/O channel 112 whenperipheral interface 172 and the I/O channel are of the same type, andthe I/O interface translates information from a format suitable to theI/O channel to a format suitable to the peripheral channel 172 when theyare of a different type. Add-on resource 174 can include a data storagesystem, an additional graphics interface, a network interface card(NIC), a sound/video processing card, another add-on resource, or acombination thereof. Add-on resource 174 can be on a main circuit board,on separate circuit board or add-in card disposed within informationhandling system 100, a device that is external to the informationhandling system, or a combination thereof.

Network interface 180 represents a NIC disposed within informationhandling system 100, on a main circuit board of the information handlingsystem, integrated onto another component such as chipset 110, inanother suitable location, or a combination thereof. Network interfacedevice 180 includes a network channel 182 that provides an interface todevices that are external to information handling system 100. In aparticular embodiment, network channel 182 is of a different type thanperipheral channel 172 and network interface 180 translates informationfrom a format suitable to the peripheral channel to a format suitable toexternal devices. An example of network channel 182 includes anInfiniBand channel, a Fibre Channel channel, a Gigabit Ethernet channel,a proprietary channel architecture, or a combination thereof. Networkchannel 182 can be connected to an external network resource (notillustrated). The network resource can include another informationhandling system, a data storage system, another network, a gridmanagement system, another suitable resource, or a combination thereof.

BMC 190 is connected to multiple elements of information handling system100 via one or more management interface 192 to provide out of bandmonitoring, maintenance, and control of the elements of the informationhandling system. As such, BMC 190 represents a processing devicedifferent from processor 102 and processor 104, which provides variousmanagement functions for information handling system 100. For example,BMC 190 may be responsible for power management, cooling management, andthe like. The term baseboard management controller (BMC) is often usedin the context of server systems, while in a consumer-level device a BMCmay be referred to as an embedded controller (EC). A BMC included at adata storage system can be referred to as a storage enclosure processor.A BMC included at a chassis of a blade server can be referred to as achassis management controller and embedded controllers included at theblades of the blade server can be referred to as blade managementcontrollers. Capabilities and functions provided by BMC 180 can varyconsiderably based on the type of information handling system. BMC 190can operate in accordance with an Intelligent Platform ManagementInterface (IPMI). Examples of BMC 190 include an Integrated Dell RemoteAccess Controller (iDRAC) or other embedded controller. Managementinterface 192 represents an out of band communication interface tobetween BMC 190 and the elements of information handling system 100, andcan include an Inter-Integrated Circuit (I2C) bus, a System ManagementBus (SMBUS), a Power Management Bus (PMBUS), or the like. As usedherein, out-of-band access refers to operations performed apart from aBIOS/operating system execution environment on information handlingsystem 100, that is apart from the execution of code by processors 102and 104 and procedures that are implemented on the information handlingsystem in response to the executed code.

FIG. 2 illustrates BIOS/EFI module 142 that includes pre-operatingsystem (OS) BIOS code, runtime BIOS code 220, POST/boot logs 230, andBIOS setting attributes 240. Pre-OS code 210 represents a portion ofsystem BIOS that operates to detect the resources of informationhandling system 100, to provide drivers for the resources, and toinitialize the resources. Pre-OS code 210 includes Power-On Self Test(POST)/boot code 212, OS loader code 214, diagnostic code 216, andremediation code 218. POST/boot code 212 operates immediately upon areset condition of information handling system 100 and performs theoperations needed to detect and initialize the resources of theinformation handling system in preparation for booting an operatingsystem (OS) on the information handling system. For example, POST/bootcode 212 can operate to verify the integrity of the POST/boot codeitself, to verify processor registers and the resources of theinformation handling system, to discover the size of the system memory,to initialize the system memory, to discover and launch extension BIOSes(e.g., option ROMs), to discover, initialize, and catalog system bussesand interfaces, and to provide a user interface 213 for configuring theavailable POST/boot options. In operation, POST/boot code 212 utilizesBIOS setting attributes 240 to determine and apply varioususer-selectable configuration options. An example of BIOS settingattributes includes various “CMOS settings” or “BIOS settings.”

Upon successful completion of the functions and procedures of POST/bootcode 212, the POST/boot code operates to pass control of informationhandling system 100 to OS loader 214 to launch an OS on informationhandling system 100, and runtime BIOS 220 operates to provide the commonaccess mechanisms for the resources of information handling system 100to the OS. During the operation of OS loader 214, POST/boot code 212continues to monitor the operation of the OS loader to determine whetheror not the OS was successfully loaded, and if errors in loading the OSare detected, the BIOS/boot code operates to pass control of informationhandling system 100 to diagnostic code 216, as described below.

If POST/boot code 212 detects any anomalies or errors in the process ofbooting information handling system 100, the POST/boot code operates toprovide an indication as to the nature of the anomaly or error. Forexample, POST/boot code can provide a POST “beep code” or a port 80write with a “POST code.” Further, POST/boot code 212 operates to writea log of anomalies or errors that are detected in the process of bootinginformation handling system 100 to POST/boot logs 230. If POST/boot code212 is able to complete the POST/boot process, in spite of the detectionof anomalies or errors, the POST/boot code operates to pass control ofinformation handling system 100 to diagnostic code 216. An example of ananomaly or boot process error includes a secure boot failure, a bootorder failure, a legacy mode/EFI mode error, a disabled disk drivefailure, a legacy option-ROM detect or install failure, a driver detector install failure, a UEFI network enabled/disabled error, a BIOS/UEFIfirmware update failure, a TPM detect or authentication failure, or thelike.

FIGS. 3 and 4 illustrate a method for diagnostic use of bios attributesto remediate configuration issues in an information handling system,starting at block 300. An information handling system begins operationafter a system reset and clears a POST failure count in block 302 andbegins the POST process by executing a first POST task in block 304. Adecision is made as to whether or not the POST task was successfullyperformed, that is, whether or not the POST task resulted in a failure,in decision block 306. If not, the “NO” branch of decision block 306 istaken and the method proceeds to decision block 314 as described below.If the POST task resulted in a failure, the “YES” branch of decisionblock 306 is taken, the failure is logged in block 308, the failurecount is incremented in block 312, and the method proceeds to decisionblock 314.

When the POST task was successfully performed, as determined in decisionblock 306, or after the failure count is incremented in block 312, adecision is made as to whether or not the POST task was the last POSTtask, that is, whether or not the POST process is done, in decisionblock 314. If not, the “NO” branch of decision block 314 is taken, anext POST task is selected in block 316, and the method returns to block304 where the next POST task is executed. If the POST process is done,the “YES” branch of decision block 314 is taken and a decision is madeas to whether or not the POST process resulted in any failures indecision block 318. If so, the “YES” branch of decision block 318 istaken and the method proceeds to block 324 as described below. If thePOST process did not result in any failures, the “NO” branch of decisionblock 318 is taken and the OS loader is launched in block 320. Adecision is made as to whether or not the OS load failed in decisionblock 322. If so, the “YES” branch of decision block 322 is taken andthe method proceeds to block 324 as described below. If the OS load didnot fail, the “NO” branch of decision block 322 is taken, the POSTprocess is exited and the BIOS hands control of the information handlingsystem to the OS in block 326, and the method ends in block 328.

If the POST process resulted in any failures, as determined in decisionblock 318, or if the OS load failed, as determined in decision block322, the diagnostic code is launched and the failure log is passed tothe diagnostic code in block 324. An error category is determined for anerror identified in the error log in block 330, and a test that istargeted by the diagnostic code as being related to the error categoryis executed in block 332. For example, BIOS/EFI module 142 may send acategory “OS Boot Failure” when the Load Failure is detected in block322. This may result in diagnostic code 216 examining resources such asmemory 120, disk controller 150, and HDD 154 resources to determine if ahardware reason exists for the OS boot problem. Thus, diagnostic code216 is designed to verify the hardware state of information handlingsystem 100. In another example, BIOS/EFI module 142 may send a category“Fan Failure” when the failure decision logic determines that coolingcomponents are not working as expected. In this instance, diagnosticcode 216 may execute all available fan tests for all possible fansources populated in the information handling system. In yet anotherexample, BIOS/EFI module 142 may send a category “Battery Failure” whichcan occur with mobile information handling systems powered by directcurrent (DC) power sources. Here, diagnostics code 216 may confirm thehealth of the physical connection and communication with the battery andcharging capability of the AC/DC conversion logic that is responsiblefor recharging operation. The use of error categories enables diagnosticcode 216 to narrow the focus of the available tests to verify thehighest probably source of failures with these least amount of timedelay.

A decision is made as to whether or not the targeted test identified thefailure as a hardware failure in decision block 336. If so, the “YES”branch of decision block 336 is taken and the method proceeds to block348 as described below. If the targeted test did not identify thefailure as a hardware failure, the “NO” branch of decision block 336 istaken and a decision is made as to whether or not the BIOS POSTindicated an error category in decision block 338. If not, the “NO”branch of decision block 338 is taken and the method proceeds to block348 as described below. If the diagnostic code can identify a setupoption related to the error category, the “YES” branch of decision block338 is taken and the remediation code is launched and the setupattribute information is retrieved by the remediation code in block 340.

For example, setup attributes for secure boot, boot order, boot mode(UEFI images or non-UEFI legacy images) and HDD enable/disable can bepossible causes for POST errors of category “OS Boot Failure” dependingon the information handling system configuration. If the error categorycan be associated with BIOS setup attributes, the “YES” branch ofdecision block 342 is taken and diagnostic will display possible optionchoices for the attribute(s) that could remedy the problem based oncurrent attribute(s) values and the state of the system. Any derivedremediation options are displayed to the user without having totransition outside of the diagnostic program. If the user accepts one ofthe offered remediation solutions, diagnostics will configure the setupattribute appropriately resulting in storage of the new setup attributevalue in block 240. The remediation code reboots the informationhandling system in block 346, and the method ends in block 328.

When the targeted test that was executed in block 332 identified thefailure as a hardware failure, as determined in decision block 336, orwhen the diagnostic code can identify a setup option related to theerror category, as determined in decision block 338, the diagnostic codedisplays a result and prompts the user for an input in block 348. Thedisplayed result can relate to the discovered hardware failure, to thelack of a setup option, or to the fact that a setup option wasdiscovered but that the information handling system was set in a manualremediation mode, depending upon which path was taken to get to block348. A decision is made as to whether or not the user provided a settingchange input in decision block 350. If not, the “NO” branch of decisionblock 350 is taken, the diagnostic code is exited in block 356, and themethod ends in block 328. If the user provided a setting change input,the “YES” branch of decision block 350 is taken, the user sets the setupattribute as determined in decision block 338 to a setting that correctsthe anomaly or error in the boot process or the OS launch process inblock 352, the user reboots the information handling system in block354, and the method ends in block 328.

For purpose of this disclosure, an information handling system caninclude any instrumentality or aggregate of instrumentalities operableto compute, classify, process, transmit, receive, retrieve, originate,switch, store, display, manifest, detect, record, reproduce, handle, orutilize any form of information, intelligence, or data for business,scientific, control, entertainment, or other purposes. For example, aninformation handling system can be a personal computer, a laptopcomputer, a smart phone, a tablet device or other consumer electronicdevice, a network server, a network storage device, a switch router orother network communication device, or any other suitable device and mayvary in size, shape, performance, functionality, and price. Further, aninformation handling system can include processing resources forexecuting machine-executable code, such as a central processing unit(CPU), a programmable logic array (PLA), an embedded device such as aSystem-on-a-Chip (SoC), or other control logic hardware. An informationhandling system can also include one or more computer-readable mediumfor storing machine-executable code, such as software or data.Additional components of an information handling system can include oneor more storage devices that can store machine-executable code, one ormore communications ports for communicating with external devices, andvarious input and output (I/O) devices, such as a keyboard, a mouse, anda video display. An information handling system can also include one ormore buses operable to transmit information between the various hardwarecomponents.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents.

When referred to as a “device,” a “module,” or the like, the embodimentsdescribed herein can be configured as hardware. For example, a portionof an information handling system device may be hardware such as, forexample, an integrated circuit (such as an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), astructured ASIC, or a device embedded on a larger chip), a card (such asa Peripheral Component Interface (PCI) card, a PCI-express card, aPersonal Computer Memory Card International Association (PCMCIA) card,or other such expansion card), or a system (such as a motherboard, asystem-on-a-chip (SoC), or a stand-alone device).

The device or module can include software, including firmware embeddedat a device, such as a Pentium class or PowerPC™ brand processor, orother such device, or software capable of operating a relevantenvironment of the information handling system. The device or module canalso include a combination of the foregoing examples of hardware orsoftware. Note that an information handling system can include anintegrated circuit or a board-level product having portions thereof thatcan also be any combination of hardware and software.

Devices, modules, resources, or programs that are in communication withone another need not be in continuous communication with each other,unless expressly specified otherwise. In addition, devices, modules,resources, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover any andall such modifications, enhancements, and other embodiments that fallwithin the scope of the present invention. Thus, to the maximum extentallowed by law, the scope of the present invention is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

What is claimed is:
 1. An information handling system, comprising: astorage device to store Power-On Self Test (POST) code, diagnostic code,and remediation code; and a processor configured to: execute the POSTcode to boot the information handling system and to determine whether anerror occurred during the boot; execute the diagnostic code if the erroroccurred, the diagnostic code to determine whether the error isassociated with a first configuration setting of the informationhandling system being in a first state; and execute the remediation codeif the error is associated with the first configuration setting being inthe first state, the remediation code to change the first configurationsetting from the first state to a second state, and to reboot theinformation handling system.
 2. The information handling system of claim1, wherein, when the error is associated with the first configurationsetting being in the first state, the processor is further configured toexecute the remediation code to determine whether the remediation codeis set to an automatic remediation state, and wherein changing the firstconfiguration setting from the first state to the second state is inresponse to the remediation code being set to the automatic remediationstate.
 3. The information handling system of claim 2, wherein, when theremediation code is not set to the automatic remediation state, theprocessor is further configured to provide an indication to that theerror is associated with the first configuration setting being in thefirst state.
 4. The information handling system of claim 1, wherein,when the error is not associated with the first configuration settingbeing in the first state, the processor is further configured to providean indication to that the error is not associated with the firstconfiguration setting being in the first state.
 5. The informationhandling system of claim 1, wherein, prior to determining whether theerror is associated with the first configuration setting being in thefirst state, the processor is further configured to execute thediagnostic code to determine whether the error is associated with ahardware device of the information handling system, and whereindetermining whether the error is associated with the first configurationsetting being in the first state is in response to determining that theerror is not associated with the hardware device.
 6. The informationhandling system of claim 5, wherein, when the error is associated withthe hardware device, the processor is further configured to provide anindication to that the error is associated with the hardware device. 7.The information handling system of claim 1, wherein the storage deviceis further to store operating system (OS) loader code, and wherein theprocessor is further configured to execute the OS loader code if noerror occurred while booting the information handling system.
 8. Theinformation handling system of claim 7, wherein, in executing the OSloader code, the processor is further configured execute the POST codeto determine whether the OS failed to load.
 9. The information handlingsystem of claim 8, wherein, if the OS failed to load, the processor isfurther configured to: execute the diagnostic code to determine whetherthe failure to load the OS is associated with a second configurationsetting of the information handling system being in a third state; andexecute the remediation code when the failure to load the OS isassociated with the second configuration setting being in the thirdstate, the remediation code further to change the second configurationsetting from the third state to a fourth state, and to reboot theinformation handling system.
 10. The information handling system ofclaim 9, wherein, when the failure to load the OS is not associated witha second configuration setting being in a third state, the processor isfurther configured to provide an indication to that the OS failed toload.
 11. A method for remediating configuration issues in aninformation handling system, the method comprising: determining, by aprocessor of the information handling system, whether an error occurredwhile booting the information handling system; determining, if the erroroccurred, whether the error is associated with a first configurationsetting of the information handling system being in a first state; andchanging, if the error is associated with the first configurationsetting being in the first state, the first configuration setting fromthe first state to a second state; and rebooting the informationhandling system.
 12. The method of claim 11, wherein, when the error isassociated with the first configuration setting being in the firststate, the method further comprises: determining whether the remediationcode is set to an automatic remediation state, wherein changing thefirst configuration setting from the first state to the second state isin response to the remediation code being set to the automaticremediation state.
 13. The method of claim 12, wherein, when theremediation code is not set to the automatic remediation state, themethod further comprises: providing, by the processor, an indication tothat the error is associated with the first configuration setting beingin the first state.
 14. The method of claim 11, wherein, when the erroris not associated with the first configuration setting being in thefirst state, the method further comprises: providing, by the processor,an indication to that the error is not associated with the firstconfiguration setting being in the first state.
 15. The method of claim11, wherein, prior to determining whether the error is associated withthe first configuration setting being in the first state, the methodfurther comprises: determining, by the processor, whether the error isassociated with a hardware device of the information handling system,wherein determining whether the error is associated with the firstconfiguration setting being in the first state is in response todetermining that the error is not associated with the hardware device.16. The method of claim 15, wherein, when the error is associated withthe hardware device, the method further comprises: providing, by theprocessor, an indication to that the error is associated with thehardware device.
 17. The method of claim 11, further comprising:executing OS loader code if no error occurred while booting theinformation handling system.
 18. The method of claim 17, wherein, inexecuting the OS loader code, the method further comprises: determining,by the processor, whether the OS failed to load.
 19. The method of claim18, wherein, if the OS failed to load, the method further comprises:determining, by the processor, whether the failure to load the OS isassociated with a second configuration setting of the informationhandling system being in a third state; changing, when the failure toload the OS is associated with the second configuration setting being inthe third state, the second configuration setting from the third stateto a fourth state; and rebooting the information handling system.
 20. Aninformation handling system, comprising: a storage device to storeoperating system (OS) loader code, diagnostic code, and remediationcode; and a processor configured to: execute the OS loader code to bootthe information handling system and to determine whether the OS failedto load on the information handling system; execute the diagnostic codeif the OS failed to load, the diagnostic code to determine whether theload failure is associated with a configuration setting of theinformation handling system being in a first state; and execute theremediation code if the error is associated with the configurationsetting being in the first state, the remediation code to change thefirst configuration setting from the first state to a second state, andto reboot the information handling system.